Method and device for displaying notification

ABSTRACT

Disclosed is an example method of displaying a notification on a device with a plurality of operating systems (OSes) installed therein. The method includes identifying a first OS displayed on a first display of the device among the plurality of OSes, detecting a notification generated in a second OS running in a background of the device among the plurality of OSes, converting the generated notification based on a preset format of the first OS when the notification is generated, and displaying the converted notification on the first display on which the first OS is displayed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/504,686, filed Jul. 8, 2019, which is a continuation of U.S. patentapplication Ser. No. 15/386,809, filed Dec. 21, 2016, now U.S. Pat. No.10,387,224, which is a continuation of International Application No.PCT/KR2016/008209, filed Jul. 27, 2016, which designated the UnitedStates and claims priority to Korean Patent Application No.10-2015-0106094, filed Jul. 27, 2015. The contents of each of theseapplications are incorporated herein in their entirety.

TECHNICAL FIELD

The present invention relates to a method of displaying a notificationon a device with a plurality of operating systems (OSes) installedtherein, a device with a plurality of OSes installed therein, and arecoding medium on which the method of displaying a notification on adevice with a plurality of OSes installed therein is recorded.

BACKGROUND ART

An operating system (OS) is a program that allows a user to use acomputer by controlling hardware and software of the computer. An OS mayfunction as an interface between hardware and application programs andmay manage computer resources, such as a central processing unit (CPU),a main memory device, an input/output device, etc.

Recently, as users desire to use various computing environmentsaccording to objectives or necessity, research into technology forrunning two or more OSes in one device is required.

SUMMARY

Embodiments disclosed herein may provide a method of displaying anotification on a device with a plurality of operating systems (OSes)installed therein, and particularly to, a method of enabling a devicewith a plurality of OSes installed therein to effectively displaynotifications of the OSes configured with different instructions.

A method of displaying a notification on a device with a plurality ofoperating systems (OSes) installed therein according to an embodimentincludes identifying a first OS displayed on a first display of thedevice among the plurality of OSes; detecting a notification generatedin a second OS running in a background of the device among the pluralityof OSes; converting the generated notification based on a preset formatof the first OS when the notification is generated; and displaying theconverted notification on the first display on which the first OS isdisplayed.

The method according to an embodiment further includes displaying thefirst OS and a third OS on the first display; and selecting the first OSfrom between the first OS and the third OS when the notification isgenerated. The converting of the generated notification includesconverting the generated notification based on the preset format of theselected first OS.

In the method according to an embodiment, the selecting of the first OSincludes identifying types of the first OS and the third OS; andselecting the first OS based on a type of the notification when thenotification is generated in the second OS.

In the method according to an embodiment, the selecting of the first OSincludes selecting the first OS based on preset priority informationindicating a priority of an OS in which the generated notification isdisplayed.

The method according to an embodiment may further include dividing ascreen area of the first display. The displaying of the first OS and athird OS includes displaying the first OS and the third OS in a firstwindow and a second window, respectively, which are obtained by dividingthe screen area.

In the method according to an embodiment, the selecting of the first OSincludes selecting the first OS based on a complexity of each of thefirst window and the second window.

The method according to an embodiment further includes stoppingdisplaying the third OS in the second window; running the third OS inthe background of the device; and converting the generated notificationbased on the preset format of the first OS when the notification isgenerated in at least one of the second OS and the third OS.

The method according to an embodiment further includes displaying afourth OS on a second display that is additionally connected to thedevice; and selecting the first OS from between the first OS and thefourth OS when the notification is generated. The converting of thegenerated notification includes converting the generated notificationbased on the preset format of the selected first OS.

The method according to an embodiment further includes detecting thesecond display. The displaying of a fourth OS on a second displayincludes displaying the fourth OS running in the background of thedevice on the second display when the second display is detected.

In the method according to an embodiment, the selecting of the first OSincludes identifying types of the first display and the second display;and selecting the first OS displayed on the selected first display basedon the identified types of the displays.

In the method according to an embodiment, the selecting of the first OSincludes selecting the first OS based on a complexity of each of thefirst display and the second display.

The method according to an embodiment further includes stoppingdisplaying the fourth OS on the second display; running the fourth OS inthe background of the device; and converting the generated notificationbased on the preset format of the first OS when the notification isgenerated in the second OS and the fourth OS.

The method according to an embodiment further includes stoppingdisplaying the first OS on the first display; displaying the second OSon the first display; detecting a notification generated in the firstOS; and displaying the notification generated in the first OS on thefirst display on which the second OS is displayed.

A device with a plurality of OSes installed therein according to anembodiment includes a first display configured to display a first OSamong the plurality of OSes; and a controller configured to identify thefirst OS displayed on the first display, detect a notification generatedin a second OS running in a background of the device among the pluralityof OSes when the notification is generated, and convert the generatednotification based on a preset format of the first OS. The first displaydisplays the converted notification.

In the device according to an embodiment, the first display displays thefirst OS and a third OS, and the controller selects the first OS frombetween the first OS and the third OS when the notification is generatedand converts the generated notification based on the preset format ofthe selected first OS.

In the device according to an embodiment, the controller identifies thefirst OS and the third OS and selects the first OS based on a type ofthe notification when the notification is generated in the second OS.

In the device according to an embodiment, the controller selects thefirst OS based on preset priority information indicating a priority ofan OS in which the generated notification is displayed.

In the device according to an embodiment, the controller divides ascreen area of the first display and displays the first OS and the thirdOS in a first window and a second window, respectively, which areobtained by dividing the screen area.

In the device according to an embodiment, the controller selects thefirst OS based on a complexity of each of the first window and thesecond window.

In the device according to an embodiment, the controller stopsdisplaying the third OS in the second window, runs the third OS in thebackground of the device, and converts the generated notification basedon the preset format of the first OS when the notification is generatedin at least one of the second OS and the third OS.

The device according to an embodiment further includes a second displayconfigured to display a fourth OS. The controller selects the first OSfrom between the first OS and the fourth OS when the notification isgenerated and converts the generated notification based on the presetformat of the selected first OS.

In the device according to an embodiment, the controller detects thesecond display and controls the second display to display the fourth OSrunning in the background of the device when the second display isdetected.

In the device according to an embodiment, the controller identifiestypes of the first display and the second display and selects the firstOS displayed on the selected first display based on the identified typesof the displays.

In the device according to an embodiment, the controller selects thefirst OS based on a complexity of each of the first display and thesecond display.

In the device according to an embodiment, the second display stopsdisplaying the fourth OS, and the controller executes the fourth OS inthe background of the device and converts the generated notificationbased on the preset format of the first OS when the notification isgenerated in the second OS and the fourth OS.

In the device according to an embodiment, the first display displays thesecond OS when the first OS stops being displayed, and the controllerdisplays a notification generated in the first OS on the first displayon which the second OS is displayed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conceptual diagram for describing a method of displaying anotification on a device with a plurality of operating systems (OSes)installed therein according to an embodiment.

FIG. 2 is a flowchart for describing a method of displaying anotification on a device with a plurality of OSes installed thereinaccording to an embodiment.

FIG. 3 is a diagram for describing a method of displaying a notificationgenerated in a second OS running in the background of a device on afirst display according to an embodiment.

FIG. 4 is a flowchart for describing a method of displaying anotification generated in a second OS when a first OS and a third OS aredisplayed on a first display of a device according to an embodiment.

FIG. 5 is a diagram for describing a method of displaying a notificationgenerated in an OS running in the background when a plurality of OSesare displayed on a first display of a device according to an embodiment.

FIG. 6 is a flowchart for describing a method of displaying anotification generated in a second OS when a first OS and a fourth OSare displayed on a first display and a second display of a deviceaccording to an embodiment.

FIG. 7 is a diagram for describing a method of displaying a notificationgenerated in an OS running in the background when a plurality of OSesare displayed on a first display and a second display of a deviceaccording to an embodiment.

FIG. 8 is a flowchart for describing a method of displaying anotification running in the background of a device when one of aplurality of OSes displayed on a first display of the device accordingto an embodiment stops being displayed.

FIGS. 9A and 9B are diagrams for describing a method of displaying anotification generated in an OS running in the background when one of aplurality of OSes displayed on a first display of a device according toan embodiment stops being displayed.

FIG. 10 is a flowchart for describing a method of displaying anotification running in the background of a device when one of aplurality of OSes displayed on a first display and a second display ofthe device according to an embodiment stops being displayed.

FIGS. 11A and 11B are diagrams for describing a method of displaying anotification of an OS running in the background of a device when one ofa plurality of OSes displayed on a first display and a second display ofthe device according to an embodiment stops being displayed.

FIG. 12 is a flowchart for describing a method of displaying anotification generated in an OS running in the background of a devicewhen a plurality of OSes are displayed by dividing a screen area of afirst display of a device according to an embodiment.

FIGS. 13A and 13B are diagrams for describing a method of displaying anotification generated in an OS running in the background of a devicewhen a plurality of OSes are displayed by dividing a screen area of afirst display of a device according to an embodiment.

FIG. 14 is a flowchart for describing a method of displaying anotification generated in an OS running in the background of a devicewhen a plurality of OSes are displayed by adding a second display to adevice according to an embodiment.

FIGS. 15A and 15B are diagrams for describing a method of displaying anotification generated in an OS running in the background of a devicewhen a plurality of OSes are displayed by adding a second display to adevice according to an embodiment.

FIG. 16 is a flowchart for describing a method of displaying anotification generated in an OS running in the background when aplurality of OSes displayed on a first display of a device are changedaccording to an embodiment.

FIGS. 17A and 17B are diagrams for describing a method of displaying anotification generated in an OS running in the background when aplurality of OSes displayed on a first display of a device are changedaccording to an embodiment.

FIGS. 18 and 19 are block diagrams showing a device with a plurality ofOSes installed therein according to an embodiment.

DETAILED DESCRIPTION

Terms used herein will be briefly described, and exemplary embodimentswill be described in detail below.

General and widely-used terms have been employed herein in considerationof functions provided in the present invention, and may vary accordingto an intention of one of ordinary skill in the art, a precedent, or theemergence of new technologies. Additionally, in some cases, theapplicant may arbitrarily select specific terms and in such a case, theapplicant will provide the meaning of the terms in the description ofthe exemplary embodiments.

Accordingly, the terms used herein should be defined on the basis of themeaning of the terms and the content of the present disclosure, insteadof the names of the terms.

Furthermore, when one part is referred to as “comprising” (or“including” or “having”) other elements, it should be understood that itcan comprise (or include or have) only those elements or other elementsas well as those elements unless specifically described otherwise.

Moreover, each of terms such as “unit” and “module” used herein denotesan element for performing at least one function or operation, and may beimplemented in hardware, software or a combination of hardware andsoftware.

Hereinafter, exemplary embodiments will be fully described withreference to the accompanying drawings in such a way that those skilledin the art can easily carry out the embodiments. The exemplaryembodiments may, however, be embodied in many different forms and arenot to be construed as being limited to the embodiments set forthherein. In the accompanying drawings, portions irrelevant to thedescription of the exemplary embodiments will be omitted for clarity.Moreover, like reference numerals refer to like elements throughout thisdisclosure.

A device described herein may include a digital television (TV), adesktop computer, a mobile phone, a smartphone, a tablet personalcomputer (PC), a laptop computer, a digital broadcasting terminal, apersonal digital assistant (PDA), a portable multimedia player (PMP), anavigation system, etc.

An operating system (OS) refers to a program that enables a user to usea device by controlling hardware and software of the device. An OS mayfunction as an interface between hardware and application programs andmay manage computer resources, such as a central processing unit (CPU),a main memory device, an input/output device, etc. Examples of the OSmay include Android, Windows, Mac, TIZEN, Unix, and Linux.

An application refers to software developed to enable a user to performa specific task using a device. For example, the application may includean email application, a messenger application, a schedule managementapplication, a document editor application, etc. Also, the applicationmay be composed of instructions needed to perform a specific task. Here,the instructions composing the application may be different depending onthe type of OS. For example, a first messenger application that is setto run on a first OS cannot run on a second OS.

A notification may be generated when an event occurs in an applicationinstalled in a device. Here, the event may include an acquisition orreception of new data by an application running in the device or acompletion of a task that was processed by an application. However, thisis merely an embodiment, and thus the event is not limited thereto. Asanother example, a version update of an application may also be anexample of the event. A notification may be output to a device in theform of at least one of text, image, video, and sound.

Hereinafter, the present invention will be described in detail withreference to the accompanying drawings.

FIG. 1 is a conceptual diagram for describing a method of displaying anotification on a device 100 having a plurality of OSes 10 and 20installed therein according to an embodiment.

The plurality of OSes 10 and 20 are installed in the device 100according to an embodiment.

For example, a first OS 10 and a second OS 20 may be installed in thedevice 100. However, this is merely an example. Two or more OSes may beinstalled in the device 100.

The device 100 according to an embodiment may store applications runningon each of the plurality of OSes. For example, the device 100 may storea first email application, a first messenger application, and the likewhich are running on the first OS. Also, the device 100 may store asecond email application, a second messenger application, a seconddocument editor application, and the like which are running on thesecond OS. Here, at least one first application running on the first OS10 and at least one second application running on the second OS 20 mayhave different types and formats of instructions composing each of theapplications.

The device 100 according to an embodiment may display the first OS 10 ona first display 110. Here, the device 100 displaying the first OS 10 onthe first display 110 denotes that the device 100 displays, on the firstdisplay 110, data output by running the first application on the firstOS 10.

According to another embodiment, the device 100 may display two or moreOSes on the first display 110. This will be described below in moredetail with reference to FIG. 5. According to still another embodiment,the device 100 may display two or more OSes on each of two or moredisplays. This will be described below in more detail with reference toFIG. 7.

Meanwhile, the device 100 according to an embodiment may enable thesecond OS 20 to run in the background of the device 100. Here, thesecond OS 20 may be one of the plurality of OSes installed in the device100. The second OS 20 running in the background of the device 100 maynot be displayed on the first display 110.

The device 100 according to an embodiment may detect a notification 22generated in the second OS 20. For example, when an event occurs in atleast one second application running on the second OS 20, thenotification 22 may be generated. Since the notification 22 is generatedin the second OS 20 that is not displayed on the first display 110, thedevice 100 may convert the generated notification 22 on the basis of aformat preset for the first OS 10. Here, an operation of converting thenotification 22 refers to an operation of converting a format of datacomposing the notification 22.

The device 100 according to an embodiment may display a convertednotification 12 on the first display 110. For example, the device 100may display the converted notification 12 at a preset position in ascreen area of the first display 110. As another example, the device 100may display the converted notification 12 in an area with low complexityout of the screen area of the first display 110. According to anembodiment, the complexity may be determined depending on the number ofexecution windows that are displayed in the screen area when anapplication runs on the device 100. For example, as the number ofexecution windows displayed in the screen area decreases, the complexitymay decrease. Examples of the execution windows may include a documenteditor window that is output when a document editor application isexecuted, a web browser window that is output when a web browserapplication is executed, etc.

FIG. 2 is a flowchart for describing a method of displaying anotification on the device 100 with a plurality of OSes installedtherein according to an embodiment.

In step S210, the device 100 identifies the first OS 10 displayed on thefirst display 110 of the device 100 from among a plurality of OSes.

The device 100 according to an embodiment may run the plurality of OSes.

For example, in order to run the plurality of OSes, the device 100 mayrun a virtual machine that provides a virtual computing environment onthe first OS. The virtual machine indicates a virtual computingexecution environment that is generated using allocated hardwareresources of a device. The virtual machine may include a second OS andat least one second application that may run on the second OS. Thedevice may run the second OS 20 as an application while running thefirst OS 10 as a host OS.

As another example, the device 100 may create virtual machines, whichare a plurality of stand-alone environments. Each of the created virtualmachines may include an independent OS and an application running on theOS. For example, a first virtual machine may include the first OS 10 anda first application that may run on the first OS. Also, a second virtualmachine may include the second OS 20 and a second application that mayrun on the second OS.

The device 100 according to an embodiment may identify the first OS 10being displayed on the first display 110 from among the plurality ofOSes. For example, the device 100 may identify the first OS 10 beingdisplayed on the first display 110 as Android.

In step S220, the device 100 detects the notification 22 generated inthe second OS 20 that is running in the background of the device 100among the plurality of OSes. The second OS 20 running in the backgroundmay be an OS that is executed by the virtual machine of the device 100but not displayed on the first display 110.

When an event occurs in the second application running on the second OS20, a notification may be generated to provide information regarding theevent to a user. For example, when a new email is received through anemail application running on a Windows OS, an email arrival notificationmay be generated. The device 100 may detect the email arrivalnotification generated in the second OS.

In step S230, when the notification 22 is generated, the device 100converts the generated notification 22 on the basis of a preset formatof the first OS 10.

According to an embodiment, information regarding the notificationgenerated in the second OS may be delivered to the first OS. In order todisplay the generated notification 22 on the first display 110, thedevice may convert the notification 22 on the basis of the preset formatof the first OS 10 displayed on the first display 110. For example, thedevice 100 may change at least one of text, image, video, and soundcomposing the notification 22 according to a format provided by thefirst OS.

In step S240, the device 100 displays the converted notification 12 onthe first display 110 on which the first OS 10 is displayed.

The device 100 according to an embodiment may display the convertednotification 12 at a preset position in a screen area of the firstdisplay 110. For example, the device 100 may display the convertednotification 12 at an upper left corner of the screen area of the firstdisplay 110.

As another example, the device 100 may display the convertednotification 12 on the first display 110 on the basis of a complexity ofthe first display 110. An execution window of the first applicationrunning on the first OS 10 may be displayed in the screen area of thefirst display 110. The device 100 may determine the complexity of thefirst display 110 on the basis of the types, number, positions, anddisplay forms of execution windows displayed in the screen area of thefirst display 110.

As still another example, the device 100 may display the convertednotification 12 on the first display 110 on the basis of the type ofconverted notification 12. For example, when a notification is generatedin an email application, the device 100 may display the convertednotification at an upper left corner of the first display 110. Also,when a notification is generated in a messenger application, the device100 may display the converted notification at an upper right corner ofthe first display 110.

FIG. 3 is a diagram for describing a method of displaying a notificationgenerated in a second OS running in the background of the device 100 onthe first display 110 according to an embodiment.

The device 100 according to an embodiment may run a plurality of OSes310, 320, and 330.

Referring to an OS structure 300 running on the device 100, OS A 310 isa host OS, which is a default OS of the device 100. Also, OS B 320 andOS C 330 are each a guest OS, which may run in the same applicationexecution manner as OS A 310. However, this is merely an example ofmethod of running the plurality of OSes 310, 320, 330 on the device 100.As another example, the device 100 may store the plurality of OSes 310,320, and 330 in a plurality of respective virtual machines and run theOSes 310, 320, and 330.

OS A 310 may be displayed on the first display 110 of the device 100.According to an embodiment, an OS to be displayed on the first display110 may be determined according to a user's selection. Also, at leastone of OS B 320 and OS C 330 may run in the background of the device100. According to an embodiment, OS B 320 and OS C 330 which are runningin the background may not be displayed on the first display 110 of thedevice 100.

The device 100 according to an embodiment may detect a notification 322generated in OS B 320 running in the background of the device 100. Forexample, when a message is received in messenger application B runningon OS B 320, the notification 322, which indicates that the message isreceived, may be generated.

Also, the device 100 may display the generated notification 322 on thefirst display 110 on which OS A 310 is displayed. The device 100according to an embodiment may convert the generated notification 322 onthe basis of a preset format of OS A 310. For example, when a messengericon image is included in the notification 322 of OS B 320, and amessenger icon image and text indicating a caller and a reception timeare included in the preset format of OS A 310, the device 100 may addthe text indicating a caller and a reception time to the notification322 and then convert the notification 322.

The device 100 according to an embodiment may display a convertednotification 312 at a preset position in the screen area of the firstdisplay 110. For example, the device 100 may display the convertednotification 312 at the upper left corner of the screen area. As anotherexample, the device 100 may display the converted notification 312 in anarea having a small number of application execution windows which aredisplayed on the basis of a complexity of the first display 110.

FIG. 4 is a flowchart for describing a method of displaying anotification generated in a second OS when a first OS and a third OS aredisplayed on the first display 110 of the device 100 according to anembodiment.

In step S410, the device 100 may display the first OS and the third OSon the first display 110.

The device 100 according to an embodiment may divide a screen area ofthe first display 110.

The device 100 may display the first OS and the third OS in a firstwindow and a second window, which are obtained by dividing the screenarea, respectively.

The device 100 according to an embodiment may select at least some OSesto be displayed on the screen area from among a plurality of OSesinstalled therein. For example, the device 100 may select an OSaccording to a preset priority that is a criterion for selecting an OSto be displayed from among the plurality of OSes. Here, the presetpriority is a ranking value of an OS displayed on a window. Thisembodiment may assume that the first OS, the second OS, and the third OSinstalled in the device 100 have a first ranking, a third ranking, and asecond ranking, respectively. When two windows are created in the firstdisplay 110, the device 100 may display the first OS and the third OS inthe first window and the second window, respectively.

As another example, the device 100 may receive a selection input from auser and display an OS corresponding to the received selection input ina window of the first display 110. For example, when the device 100receives a selection input which selects the first OS and the third OSfrom the user, the device 100 may display the first OS and the third OSin the first window and the second window, respectively.

In this case, the types of OSes to be displayed in windows may beselected according to the selection input of the user. For example, thedevice 100 may display the third OS in the first window and display thefirst OS in the second window on the basis of the selection input of theuser.

In step S420, the device 100 may detect a notification generated in thesecond OS running in the background of the device 100.

According to an embodiment, when an event occurs in the secondapplication running on the second OS, a notification may be generated toprovide information regarding the event to the user. Here, the second OSis merely an example for describing an OS running in the background ofthe device 100. The plurality of OSes may run in the background of thedevice 100.

Step S420 may correspond to step S220, which has been described abovewith reference to FIG. 2.

In step S430, the device 100 may select the first OS from between thefirst OS and the third OS when the notification is generated.

The device 100 according to an embodiment may select an OS fordisplaying the generated notification from among the plurality of OSesdisplayed on the display 110. For example, the device 100 may select thefirst OS with a highest priority on the basis of preset priorityinformation for selecting an OS in which the notification is to bedisplayed.

As another example, the device 100 may select the first OS on the basisof a complexity of each of the first window and the second window inwhich the first OS and the third OS are respectively displayed. Thecomplexity may be determined depending on the number of executionwindows that are displayed in a screen area when an application runs onthe device 100. As the number of execution windows displayed in thewindow decreases, the complexity may decrease. For example, the device100 may select the first OS displayed in the first window with a lowercomplexity than the second window.

As still another example, an OS in which the generated notification isto be displayed may be preset in the device 100. The device 100 mayselect the first OS preset for the second OS when the notification isgenerated in the second OS.

As still another example, the device 100 may select the OS in which thegenerated notification is to be displayed on the basis of the type ofapplication in which the notification is generated. For example, whenthe notification is generated in a messenger application of the secondOS, the device 100 may select the first OS preset for the messengerapplication.

When the notification is generated in an email application, the device100 may select the third OS preset for the email application.

In step S440, the device 100 may convert the generated notification onthe basis of a format preset for the selected first OS.

According to an embodiment, in order to display the generatednotification on the first display 110, the device 100 may convert thenotification on the basis of the preset format of the first OS displayedon the first display 110. The device 100 may change at least one oftext, image, video, and sound composing the notification according to aformat provided by the first OS. Here, the format may indicate the type,arrangement, and form of data composing the format. However, this ismerely an embodiment, and the present invention is not limited thereto.

For example, the device 100 may change the type of data composing thegenerated notification. For the messenger application of the second OS,a notification that is generated when a message is received may includetext indicating a sender and a title of the message and a profilephotograph image of the sender. Meanwhile, the preset format of theselected first OS may not include the text indicating the title of themessage. The device 100 may convert the notification such that thesender of the message and the profile photograph image of the sender areincluded by deleting the text indicating the title that is included inthe generated notification.

As another example, the device 100 may change an arrangement of datacomposing the generated notification. For the email application of thesecond OS, a notification that is generated when an email is receivedmay be set such that text indicating a sender and a title of the emailare sequentially arranged. Meanwhile, the preset format of the selectedfirst OS may be set such that the text indicating the title and thesender of the email are sequentially arranged. The device 100 mayconvert the notification such that the order of the sequentialarrangement of the text indicating the sender the title of the email ischanged in the generated notification.

As still another example, the device 100 may change the type of datacomposing the generated notification. For the email application of thesecond OS, a notification that is generated when an email is receivedmay include text indicating a sender of the email and a photograph imageof the sender. Meanwhile, the preset format of the selected first OS mayinclude text indicating the sender and a title of the email. The device100 may convert the notification by removing the photograph image of thesender from the generated notification and adding text indicating thetitle of the email to the generated notification.

However, the operation of converting the above-described notification ismerely an example for describing the present invention, and the presentinvention is not limited thereto.

In step S450, the device 100 may display the converted notification onthe first display 110 on which the first OS is displayed.

The device 100 according to an embodiment may display the convertednotification at a preset position in the first window of the firstdisplay 110. As another example, the device 100 may display theconverted notification at the determined position in the first window onthe basis of a complexity of the first window. As still another example,the device 100 may display the converted notification at the determinedposition in the first window on the basis of the type of convertednotification.

Meanwhile, step S450 may correspond to step S240, which has beendescribed above with reference to FIG. 2.

FIG. 5 is a diagram for describing a method of displaying a notification522 generated in an OS 520 running in the background when a plurality ofOSes 510 to 530 are displayed on a first display 110 of a device 100according to an embodiment.

The device 100 according to an embodiment may run the plurality of OSes510, 520, and 530.

Referring to an OS structure 500 running on the device 100, among theplurality of OSes 510, 520, and 530, OS A 510 is a host OS, and OS B 520and OS C 530 are each a guest OS. Here, the method of operating theplurality of OSes 510, 520, and 530 may be the same as described abovewith reference to FIG. 3.

The device 100 according to an embodiment may divide a screen area ofthe first display 110 to create a first window 111 and a second window112. The device 100 may display different OSes in the first window 111and the second window 112. For example, OS A 510 may be displayed in thefirst window 111, and OS C 530 may be displayed in the second window112.

According to an embodiment, an OS to be displayed on the first display110 may be determined according to a user's selection. As anotherexample, the device 100 may display OS A 510 and OS C 530 on the firstdisplay 110 on the basis of priority information regarding the order ofOSes to be displayed on the first display 110, which is preset for thedevice 100.

According to an embodiment, OS B 520 may run in the background of thedevice 100. OS B 520 which is running in the background may not bedisplayed on the first display 110 of the device 100.

Meanwhile, when an event occurs in applications of the plurality of OSes510, 520, and 530 installed in the device 100, notifications 512, 514,522, and 532 may be generated.

For example, when a message is received in a first messenger applicationrunning on OS A 510, a first message notification 512 may be generated.Also, when an email is received in a first email application running onOS A 510, a first email notification 514 may be generated.

Also, when an email is received in a second email application running onOS B 520, a second email notification 522 may be generated. Also, when amessage is received in a third messenger application running on OS C530, a third message notification 532 may be generated.

The device 100 according to an embodiment may display the notifications512 and 514 generated in OS A 510 in the first window 111 in which OS A510 is displayed. Also, the device 100 may display the notification 532generated in OS C 530 in the second window 112 in which OS C 530 isdisplayed.

The device 100 according to an embodiment may convert the second emailnotification 522 generated in OS B 520 running in the background. Thedevice 100 according to an embodiment may convert the generated secondemail notification 522 on the basis of a preset format of an OS selectedfrom between OS A 510 and OS C 530. For example, the device 100 mayselect OS C 530 with low complexity on the basis of a complexity of eachof the windows 111 and 112 in which OS A 1310 and OS C 1330 arerespectively displayed. Here, the complexity may be determined dependingon the number of execution windows that are displayed in the windowswhen an application runs on the device 100. In FIG. 5, two executionwindows may be displayed in the first window 111 when two notifications512 and 514 are generated in OS A 510. Meanwhile, one execution windowmay be displayed in the second window 112 when one notification 532 isgenerated in OS C 530. Here, the complexity of the second window 112, inwhich a relatively small number of execution windows are displayedcompared to the first window 111, may be lower than that of the firstwindow 111. Accordingly, the device 100 may select OS C 530. However,this is merely an embodiment, and the method of selecting the OS forconverting the notification by the device 100 is not limited thereto.

The device 100 according to an embodiment may convert the notification522 generated in OS B 520 on the basis of a preset format of theselected OS C 530. For example, the second email notification 522 of OSB 520 may include text indicating a sender of an email and an email iconimage, and the preset format of OS C 530 may include an email iconimage, text indicating the sender and a reception time. By adding thetext indicating the reception time to the notification 522 generated inOS B 520, the device 100 may convert the notification 522.

The device 100 according to an embodiment may display a convertednotification 534 at a preset position in the second window 112 of thefirst display 110. For example, the device 100 may display the convertednotification 534 at the center of the second window 112 at which thenumber of execution windows displayed in the second window 112 is small.

FIG. 6 is a flowchart for describing a method of displaying anotification generated in a second OS when a first OS and a fourth OSare displayed on a first display and a second display of the device 100according to an embodiment.

In step S610, the device 100 may display the first OS and the fourth OSon the first display and the second display, respectively.

The device 100 according to an embodiment may display at least some of aplurality of OSes on a plurality of displays. Here, the plurality ofdisplays may be independently installed in the device 100. As anotherexample, some of the plurality of displays may be installed in thedevice 100, and the others may be installed in an external deviceconnected with the device 100. As still another example, the pluralityof displays may be installed in an external device connected with thedevice 100.

The device 100 according to an embodiment may select a plurality of OSesto be displayed on the first display and the second display. Forexample, the device 100 may select an OS according to a preset prioritythat is a criterion for selecting an OS to be displayed from among theplurality of OSes. Here, the preset priority is a ranking value of an OSdisplayed on a display. This embodiment may assume that the first OS, asecond OS, a third OS, and the fourth OS installed in the device 100have a first ranking, a third ranking, a fourth ranking, and a secondranking, respectively. For example, the device 100 may display the firstOS and the fourth OS on the first display and the second display,respectively.

As another example, the device 100 may receive a selection input from auser and display an OS corresponding to the received selection input onthe first display and the second display.

For example, when the device 100 receives a selection input whichselects the first OS and the fourth OS from the user, the device 100 maydisplay the first OS and the fourth OS on the first window and thesecond window, respectively.

In this case, the types of OSes to be displayed in windows may beselected according to the selection input of the user. For example, thedevice 100 may display the fourth OS on the first display and maydisplay the first OS on the second display on the basis of the selectioninput of the user.

In step S620, the device 100 may detect a notification generated in thesecond OS running in the background of the device 100.

According to an embodiment, when an event occurs in the secondapplication running on the second OS, a notification may be generated toprovide information regarding the event to the user. Here, the second OSis merely an example for describing an OS running in the background ofthe device 100. The plurality of OSes may run in the background of thedevice 100.

Step S620 may correspond to step S220, which has been described abovewith reference to FIG. 2.

In step S630, the device 100 may select the first OS from between thefirst OS and the fourth OS when the notification is generated.

The device 100 according to an embodiment may select an OS fordisplaying the generated notification from between the first OS and thefourth OS. For example, the device 100 may select the first OS with ahighest priority on the basis of preset priority information forselecting an OS in which the notification is to be displayed.

As another example, the device 100 may select the first OS on the basisof a complexity of each of the first display and the second display inwhich the first OS and the fourth OS are displayed. The complexity maybe determined depending on the number of execution windows that aredisplayed in a window when an application runs on the device 100. As thenumber of execution windows displayed in the window decreases, thecomplexity may decrease. For example, the device 100 may select thefirst OS displayed in the first display with a lower complexity than thesecond display.

As still another example, an OS in which the generated notification isto be displayed may be preset in the device 100. The device 100 mayselect the first OS preset for the second OS when the notification isgenerated in the second OS.

As still another example, the device 100 may select the OS in which thegenerated notification is to be displayed on the basis of the type ofapplication in which the notification is generated. For example, whenthe notification is generated in a messenger application of the secondOS, the device 100 may select the first OS preset for the messengerapplication. When the notification is generated in an email application,the device 100 may select the fourth OS preset for the emailapplication.

In step S640, the device 100 may convert the generated notification onthe basis of a format preset for the selected first OS.

According to an embodiment, in order to display the generatednotification on the first display 110, the device 100 may convert thenotification on the basis of the preset format of the first OS displayedon the first display 110. The device 100 may change at least one oftext, image, video, and sound composing the notification according to aformat provided by the first OS. Here, the format may indicate the type,arrangement, and form of data composing the format. However, this ismerely an embodiment, and the present invention is not limited thereto.

Meanwhile, the method of converting the generated notification on thebasis of the preset format of the first OS by the device 100 maycorrespond to the above-described method with reference to FIG. 4.

In step S650, the device 100 may display the converted notification onthe first display 110 on which the first OS is displayed.

The device 100 according to an embodiment may display the convertednotification at a preset position in a screen area of the first display110. As another example, the device 100 may display the convertednotification on the first display 110 on the basis of the complexity ofthe first display 110. As still another example, the device 100 maydisplay the converted notification on the first display 110 on the basisof the type of converted notification.

Meanwhile, step S650 may correspond to step S240, which has beendescribed above with reference to FIG. 2.

FIG. 7 is a diagram for describing a method of displaying a notification722 generated in an OS 720 running in the background when a plurality ofOSes 710 to 740 are displayed on the first display 110 and a seconddisplay 115 of the device 100 according to an embodiment.

The device 100 according to an embodiment may run the plurality of OSes710, 720, 730, and 740. Referring to an OS structure 700 running on thedevice 100, among the plurality of OSes 710, 720, 730, and 740, OS A 710is a host OS, and OS B 720, OS C 730, and OS D 740 are each a guest OS.Here, the method of operating the plurality of OSes 710, 720, 730, and740 may be the same as described above with reference to FIG. 3.

According to an embodiment, the first display 110 may be installed inthe device 100, and the second display 115 may be installed in anexternal device connected with the device 100. The device 100 maydisplay different OSes on the first display 110 and the second display115.

For example, OS A 710 may be displayed on the first display 110, and OSD 740 may be displayed on the second display 115.

According to an embodiment, OSes to be displayed on the first display110 and the second display 115 may be determined according to a user'sselection. As another example, the device 100 may respectively displayOS A 710 and OS D 740 on the first display 110 and the second display115 on the basis of priority information regarding the order of OSes tobe displayed on the first display 110 and the second display 120, whichis preset for the device 100.

According to an embodiment, OS B 720 and OS C 730 may run in thebackground of the device 100. OS B 720 and OS C 730 running in thebackground of the device 100 may not be displayed on the first display110 and the second display 115.

Meanwhile, when an event occurs in applications of the plurality of OSes710, 720, 730, and 740 installed in the device 100, notifications 712,714, 722, and 742 may be generated.

For example, when a message is received in a first messenger applicationrunning on OS A 710, a first message notification 712 may be generated.Also, when an email is received in a first email application running onOS A 710, a first email notification 714 may be generated.

Also, when an email is received in a second email application running onOS B 720, a second email notification 722 may be generated. Also, when amessage is received in a fourth messenger application running on OS D740, a fourth message notification 742 may be generated.

The device 100 according to an embodiment may display the notifications712 and 714 generated in OS A 710 on the first display 110 on which OS A714 is displayed. Also, the device 100 may display the notification 740generated in OS D 740 on the second display 115 on which OS D 740 isdisplayed.

The device 100 according to an embodiment may convert the second emailnotification 722 generated in OS B 720 running in the background. Thedevice 100 may display a converted notification 744 on at least one ofthe first display 110 on which OS A 710 is displayed and the seconddisplay 115 on which OS D 740 is displayed. For example, the device 100may select OS D 740 to display the converted notification 744 on thebasis of a complexity of each of the displays 110 and 115 on which OS A710 and OS D 740 are respectively displayed.

Here, the complexity may be determined depending on the number ofexecution windows that are displayed in a screen area when anapplication runs on the device 100. For example, two execution windowsmay be displayed on the first display 110 when two notifications 712 and714 are generated in OS A 710.

Meanwhile, one execution window may be displayed on the second display115 when one notification 742 is generated in OS D 740. Here, thecomplexity of the second display 115, on which a relatively small numberof execution windows are displayed compared to the first display 110,may be lower than that of the first display 110. Accordingly, the device100 may select OS D 740 displayed on the second display 115. However,this is merely an embodiment, and the method of selecting the OS forconverting the notification by the device 100 is not limited thereto.

The device 100 according to an embodiment may convert the notification722 generated in OS B 520 on the basis of the preset format of theselected OS D 740. For example, the second email notification 722 of OSB 720 may include text indicating a sender of an email and an email iconimage, and the preset format of OS D 740 may include an email icon imageand text indicating the sender and a reception time. By adding the textindicating the reception time to the notification 722 generated in OS B720, the device 100 may convert the notification 722.

The device 100 according to an embodiment may display the convertednotification 744 at a preset position in the second display 115. Forexample, the device 100 may display the converted notification 744 at anupper right corner, which has a small number of execution windowsdisplayed in a screen area of the second display 115.

FIG. 8 is a flowchart for describing a method of displaying anotification running in the background of the device 100 when one of aplurality of OSes displayed on the first display 110 of the device 100according to an embodiment stops being displayed.

In step S810, the device 100 may display a first OS and a third OS in afirst window and a second window of the first display, respectively.

The device 100 according to an embodiment may divide a screen area ofthe first display 110.

The device 100 may display the first OS and the third OS in the firstwindow and the second window, which are obtained by dividing the screenarea, respectively.

Meanwhile, step S810 may correspond to step S410, which has beendescribed above with reference to FIG. 4.

In step S820, the device 100 may stop displaying the third OS in thesecond window.

The device 100 according to an embodiment may receive a change input forrequesting a change of the OS displayed on the first display 110 of thedevice 100 from a user. Here, the change input may include informationregarding the number of windows created in the first display 110, thetype of OSes displayed in the windows, etc.

When the device 100 according to an embodiment receives the change inputfrom the user, the device 100 may remove one of the two windows thathave already been created. Also, when the window is removed, the device100 may stop displaying an OS that is displayed in the window. Forexample, when the second window is removed from the first window and thesecond window, the device 100 may stop displaying a third OS that isdisplayed in the second window.

However, this is merely an embodiment. When the device 100 receives thechange input from the user, the device 100 may create an additionalwindow and change an OS displayed in the window.

In step S830, when the device 100 stops displaying the third OS, thedevice 100 may run the third OS in the background of the device 100.

When the third OS stops being displayed in the device 100 according toan embodiment, only the first OS among the plurality of OSes may bedisplayed on the first display 110 of the device 100, and a second OSand the third OS may run in the background of the device 100.

In step S840, when a notification is generated in at least one of thesecond OS and the third OS that are running in the background of thedevice 100, the device 100 may convert the generated notification on thebasis of a preset format of the first OS.

According to an embodiment, the second OS of the device 100 may run aplurality of second applications. When an event occurs in at least oneof the plurality of second applications, a notification for informingthe user of the event occurrence may be generated. Also, the third OS ofthe device 100 may run a plurality of third applications. When an eventoccurs in at least one of the plurality of third applications, anotification for informing the user of the event occurrence may begenerated.

Meanwhile, according to an embodiment, the device 100 may convert thenotification on the basis of the preset format of the first OS displayedon the first display 110 to display the generated notification on thefirst display 110. The device 100 may change at least one of text,image, video, and sound composing the notification according to a formatprovided by the first OS.

Meanwhile, the method of converting the generated notification on thebasis of the preset format of the first OS by the device 100 maycorrespond to the above-described method with reference to FIG. 4.

In step S850, the device 100 may display the converted notification onthe first display 110 on which the first OS is displayed.

The device 100 according to an embodiment may display the convertednotification at a preset position in a screen area of the first display110. As another example, the device 100 may display the convertednotification on the first display 110 on the basis of a complexity ofthe first display 110. As still another example, the device 100 maydisplay the converted notification on the first display 110 on the basisof the type of converted notification.

Meanwhile, step S850 may correspond to step S240, which has beendescribed above with reference to FIG. 2.

FIG. 9 is a diagram for describing a method of displaying a notification932 generated in an OS 920 or 930 running in the background when one ofa plurality of OSes 910 to 930 displayed on the first display 110 of thedevice 100 according to an embodiment stops being displayed.

The device 100 according to an embodiment may run the plurality of OSes910, 920, and 930.

Referring to an OS structure 900 running on the device 100, among theplurality of OSes 910, 920, and 930, OS A 910 is a host OS, and OS B 920and OS C 930 are each a guest OS. Here, the method of operating theplurality of OSes 910, 920, and 930 may be the same as described abovewith reference to FIG. 3.

Referring to FIG. 9A, the device 100 according to an embodiment maydivide a screen area of the first display 110 to generate the firstwindow 111 and the second window 112. The device 100 may displaydifferent OSes in the first window 111 and the second window 112.

For example, OS A 910 may be displayed in the first window 111, and OS C930 may be displayed in the second window 112.

According to an embodiment, OS B 920 may run in the background of thedevice 100. OS B 920 which is running in the background may not bedisplayed on the first display 110 of the device 100.

Meanwhile, when an event occurs in applications running on OS A 910 ofthe device 100 according to an embodiment, notifications 912 and 914 maybe generated.

For example, when a message is received in a first messenger applicationrunning on OS A 910, a first message notification 912 may be generated.Also, when an email is received in a first email application running onOS A 910, a first email notification 914 may be generated.

Also, when an email is received in a third email application running onOS C 930, a third email notification 932 may be generated.

The device 100 according to an embodiment may display the notifications912 and 914 generated in OS A 910 in the first window 111 in which OS A910 is displayed. Also, the device 100 may display the notification 932generated in OS C 930 in the second window 112 in which OS C 930 isdisplayed.

Referring to FIG. 9B, the device 100 according to an embodiment mayremove the second window 112 and may stop displaying OS C 930. Forexample, the device 100 may receive a change input for requesting achange of the OS displayed on the first display 110 of the device 100from a user. This embodiment assumes that the change input includes acommand for removing the second window 112.

When the change input is received from the user, the device 100 mayremove the second window 112 that is displayed on the first display 110.Also, when the second window 112 is removed, the device may stopdisplaying OS C 930 that is displayed in the second window 112.

When the device 100 according to an embodiment stops displaying OS C930, the device 100 may run OS C 930 in the background of the device100.

When the third OS stops being displayed in the device 100 according toan embodiment, only OS A 910 among the plurality of OSes 910, 920, and930 may be displayed on the first display 110 of the device 100, and OSB 920 and OS C 930 may run in the background of the device 100.

Meanwhile, when the second window 112 is removed, the device 100according to an embodiment may detect the notification 932 generatedfrom OS C 930 running in the background. The device 100 may convert thedetected notification 932 on the basis of a format preset for OS A 910displayed on the first display 110. For example, the third emailnotification 932 of OS C 930 may include text indicating a sender of anemail and an email icon image, and the preset format of OS A 910 mayinclude an email icon image, text indicating the sender and a receptiontime. By adding the text indicating the reception time to thenotification 932 generated in OS C 930, the device 100 may convert thenotification 932.

The device 100 according to an embodiment may display a convertednotification 916 at a preset position in the first display 110. Asanother example, the device 100 may display the converted notification916 at a predetermined position on the basis of a complexity of thefirst display 110. For example, the device 100 may display the convertednotification 916 at an upper right corner, which has a small number ofexecution windows displayed in the screen area of the first display 110.

FIG. 10 is a flowchart for describing a method of displaying anotification running in the background of the device 100 when one of aplurality of OSes displayed on the first display 110 and the seconddisplay 115 of the device 100 according to an embodiment stops beingdisplayed.

In step S1010, the device 100 may display a first OS and a fourth OS onthe first display 110 and the second display 115 of the device 100,respectively.

According to an embodiment, a plurality of OSes may be installed in thedevice 100. The device 100 may display the first OS and the fourth OSamong the plurality of OSes on the first display 110 and the seconddisplay 115, respectively.

Step S1010 may correspond to step S610, which has been described abovewith reference to FIG. 6.

In step S1020, the device 100 may stop displaying the fourth OS on thesecond display 115.

The device 100 according to an embodiment may receive a change input forrequesting a change of the OS displayed on the second display 115 of thedevice 100 from a user. Here, the change input may include informationregarding the number of displays on which OSes are displayed, the typesof OSes displayed on the displays, etc.

As another example, the device 100 may detect a disconnection from someof a plurality of displays. The device 100 may stop displaying OSes onthe displays from which the device 100 is disconnected. For example,when the device 100 is disconnected from the second display 115, thedevice 100 may stop displaying the fourth OS.

As still another example, the device 100 may stop displaying data onsome of the plurality of displays. For example, when the device 100receives an input for stopping a provision of power to the seconddisplay from the user, the device 100 may stop displaying the fourth OSon the second display 115.

In step S1030, when the device 100 stops displaying the fourth OS, thedevice 100 may run the fourth OS in the background of the device 100.

When the fourth OS stops being displayed in the device 100 according toan embodiment, only the first OS among the plurality of OSes may bedisplayed on the first display 110 of the device 100, and a second OS, athird OS, and the fourth OS may run in the background of the device 100.

In step S1040, when a notification is generated in at least one of thesecond OS, the third OS, and the fourth OS that are running in thebackground of the device 100, the device 100 may convert the generatednotification on the basis of a preset format of the first OS.

According to an embodiment, the second OS of the device 100 may run aplurality of second applications. When an event occurs in at least oneof the plurality of second applications, a notification for informingthe user of the event occurrence may be generated. Also, the third OS ofthe device 100 may run a plurality of third applications. When an eventoccurs in at least one of the plurality of third applications, anotification for informing the user of the event occurrence may begenerated. Also, the fourth OS of the device 100 may run a plurality offourth applications. When an event occurs in at least one of theplurality of fourth applications, a notification for informing the userof the event occurrence may be generated.

Meanwhile, according to an embodiment, the device 100 may convert thenotification on the basis of the preset format of the first OS displayedon the first display 110 to display the generated notification on thefirst display 110. The device 100 may change at least one of text,image, video, and sound composing the notification according to a formatprovided by the first OS.

Meanwhile, the method of converting the generated notification on thebasis of the preset format of the first OS by the device 100 maycorrespond to the above-described method with reference to FIG. 4.

In step S1050, the device 100 may display the converted notification onthe first display 110 on which the first OS is displayed.

The device 100 according to an embodiment may display the convertednotification at a preset position in a screen area of the first display110. As another example, the device 100 may display the convertednotification on the first display 110 on the basis of a complexity ofthe first display 110. As still another example, the device 100 maydisplay the converted notification on the first display 110 on the basisof the type of converted notification.

Meanwhile, step S1050 may correspond to step S240, which has beendescribed above with reference to FIG. 2.

FIG. 11 is a diagram for describing a method of displaying notifications1122 and 1142 of OSes 1120, 1130, and 1140 running in the background ofthe device 100 when one of a plurality of OSes 1110 to 1140 displayed onthe first display 110 and the second display 115 of the device 100according to an embodiment stops being displayed.

The device 100 according to an embodiment may run the plurality of OSes1110, 1120, 1130, and 1140. Referring to an OS structure 1100 running onthe device 100, among the plurality of OSes 1110, 1120, 1130, and 1140,OS A 1110 is a host OS, and OS B 1120, OS C 1130, and OS D 1140 are eacha guest OS. Here, the method of operating the plurality of OSes 1110,1120, 1130, and 1140 may be the same as described above with referenceto FIG. 3.

Referring to FIG. 11A, according to an embodiment, the first display 110may be installed in the device 100, and the second display 115 may beinstalled in an external device connected to the device 100. The device100 may display different OSes on the first display 110 and the seconddisplay 115. For example, OS A 1110 may be displayed on the firstdisplay 110, and OS D 1140 may be displayed on the second display 115.

Meanwhile, when an event occurs in applications running on OS A 1110 ofthe device 100 according to an embodiment, notifications 1112 and 1114may be generated. For example, when a message is received in a firstmessenger application running on OS A 1110, a first message notification1112 may be generated. Also, when an email is received in a first emailapplication running on OS A 1110, a first email notification 1114 may begenerated.

Also, when an email is received in a second email application running onOS B 1120, a second email notification 1132 may be generated. Also, whena message is received in a fourth messenger application running on OS D1140, a fourth message notification 1142 may be generated.

The device 100 according to an embodiment may display the notifications1112 and 1114 generated in OS A 1110 on the first display 110 on whichOS A 1110 is displayed. Also, the device 100 may convert thenotification 1122 generated in OS B 1120 running in the backgroundaccording to a format preset for OS D 1140 and may display the convertednotification on the second display 115. Here, when OS B 1120 is runningin the background of the device 100, the generated notification may bepreset such that the generated notification is displayed on the seconddisplay 115 on which OS D 1140 is displayed. Also, the device 100 maydisplay the notification 1142 generated in OS D 1140 on the seconddisplay 115 on which OS D 1140 is displayed.

Referring to FIG. 11B, the device 100 according to an embodiment maystop displaying OS D 1140 when the device 100 is disconnected from thesecond display 115.

When the device 100 according to an embodiment stops displaying OS D1140, the device 100 may run OS D 1140 in the background of the device100.

When OS D 1140 stops being displayed in the device 100 according to anembodiment, only OS A 1110 among the plurality of OSes 1110, 1120, 1130,and 1140 may be displayed on the first display 110 of the device 100,and OS B 1120, OS C 1130, and OS D 1140 may run in the background of thedevice 100.

The device 100 according to an embodiment may detect notifications 1122and 1142 generated in OS B 1120 and OS D 1140, respectively, running inthe background of the device 100. The device 100 may convert thedetected notifications 1122 and 1142 on the basis of a format preset forOS A 1110 displayed on the first display 110.

For example, the second email notification 1122 of OS B 1120 may includetext indicating a sender and a reception time of an email and an emailicon image, and the preset format of OS A 1110 may include an email iconimage and text indicating the sender. Also, for the second emailnotification 1122 of OS B 1120, the image is positioned on a right side,and the text is positioned on a left side. For the preset format of OS A1110, the image is positioned on the left side, and the text ispositioned on the right side. By deleting the text indicating thereception time from the second email notification 1122 and changing anarrangement of the text and the image, the device 100 may convert thenotification 1122.

Also, the fourth message notification 1142 of OS D 1140 may include asender of a message, details of the message, and a messenger icon image,and the preset format of OS A 1110 may include a messenger icon imageand text indicating the sender. Also, for the fourth messengernotification 1142 of OS D 1140, the image is positioned on the rightside, and the text is positioned on the left side. For the preset formatof OS A 1110, the image is positioned on the left side, and the text ispositioned on the right side. By deleting the text indicating thedetails from the fourth email notification 1142 and changing anarrangement of the text and the image, the device 100 may convert thenotification 1142.

The device 100 according to an embodiment may display convertednotifications 1146 and 1148 at a preset position in the first display110. As another example, the device 100 may display the convertednotifications 1146 and 1148 at a predetermined position on the basis ofa complexity of the first display 110. For example, the device 100 maydisplay the converted notifications 1146 and 1148 on the right side,which has a small number of application execution windows displayed in ascreen area of the first display 110.

FIG. 12 is a flowchart for describing a method of displaying anotification generated in an OS running in the background of the device100 when a plurality of OSes are displayed by dividing a screen area ofthe first display 110 of the device 100 according to an embodiment.

In step S1210, the device 100 may divide a screen area of the firstdisplay 110.

The device 100 may divide the screen area of the first display 110 onthe basis of an input received from a user. When the screen area of thefirst display 110 is divided, two windows capable of independentlydisplaying OSes may be generated.

In step S1220, the device 100 may display a first OS and a third OS inthe first window 111 and the second window 112 of the first display 110,respectively.

The device 100 according to an embodiment may select at least some OSesto be displayed on the screen area from among a plurality of OSesinstalled therein. For example, the device 100 may select an OSaccording to a preset priority that is a criterion for selecting an OSto be displayed from among the plurality of OSes. As another example,the device 100 may receive a selection input from the user and displayan OS corresponding to the received selection input in a window of thefirst display 110.

Meanwhile, step S1220 may correspond to step S410, which has beendescribed above with reference to FIG. 4.

In step S1230, the device 100 may detect a notification generated in asecond OS running in the background of the device 100.

According to an embodiment, when an event occurs in the secondapplication running on the second OS, a notification may be generated toprovide information regarding the event to the user. Here, the second OSis merely an example for describing an OS running in the background ofthe device 100. The plurality of OSes may run in the background of thedevice 100.

Meanwhile, step S1230 may correspond to step S420, which has beendescribed above with reference to FIG. 4.

In step S1240, the device 100 may select the first OS from between thefirst OS and the third OS when the notification is generated.

The device 100 according to an embodiment may select an OS fordisplaying the generated notification from among the plurality of OSesdisplayed on the display 110. For example, the device 100 may select thefirst OS with a highest priority on the basis of preset priorityinformation for selecting an OS in which the notification is to bedisplayed. As another example, the device 100 may select the first OS onthe basis of a complexity of each of the first window and the secondwindow in which the first OS and the third OS are respectivelydisplayed. As still another example, an OS in which the generatednotification is to be displayed may be preset in the device 100. Asstill another example, the device 100 may select the OS in which thegenerated notification is to be displayed on the basis of the type ofapplication in which the notification is generated.

Meanwhile, step S1240 may correspond to step S430, which has beendescribed above with reference to FIG. 4.

In step S1250, the device 100 may convert the generated notification onthe basis of a format preset for the selected first OS.

According to an embodiment, the device 100 may convert the notificationon the basis of the preset format of the first OS displayed on the firstdisplay 110 to display the generated notification on the first display110.

Meanwhile, step S1250 may correspond to step S440, which has beendescribed above with reference to FIG. 4.

In step S1260, the device 100 may display the converted notification inthe first window 111 of the first display 110 on which the first OS isdisplayed.

The device 100 according to an embodiment may display the convertednotification at a preset position in the first window 111. As anotherexample, the device 100 may display the converted notification at thedetermined position in the first window 111 on the basis of a complexityof the first window 111. As still another example, the device 100 maydisplay the converted notification at the determined position in thefirst window 111 on the basis of the type of converted notification.

Meanwhile, step S1260 may correspond to step S450, which has beendescribed above with reference to FIG. 4.

FIG. 13 is a diagram for describing a method of displaying anotification generated in an OS running in the background of the device100 when a plurality of OSes are displayed by dividing a screen area ofthe first display 110 of the device 100 according to an embodiment.

The device 100 according to an embodiment may run a plurality of OSes1310, 1320, and 1330. Referring to an OS structure 1300 running on thedevice 100, among the plurality of OSes 1310, 1320, and 1330, OS A 1310is a host OS, and OS B 520 and OS C 1330 are each a guest OS. Here, themethod of operating the plurality of OSes 1310, 1320, and 1330 may bethe same as described above with reference to FIG. 3.

Referring to FIG. 13A, when an event occurs in applications running onOS A 1310 of the device 100 according to an embodiment, notifications1312 and 1314 may be generated. For example, when a message is receivedin a first messenger application running on OS A 1310, a first messagenotification 1312 may be generated. Also, when an email is received in afirst email application running on OS A 1310, a first email notification1314 may be generated.

Also, when an email is received in a second email application running onOS B 1320, a second email notification 1322 may be generated.

The device 100 according to an embodiment may display the notifications1312 and 1314 generated in OS A 1310 on the first display 110 on whichOS A 1310 is displayed. Also, the device 100 may convert thenotification 1322 generated in OS B 1320 running in the backgroundaccording to a format preset for OS A 1310 and may display the convertednotification on the first display 110.

Referring to FIG. 13B, The device 100 according to an embodiment maydivide a screen area of the first display 110 on the basis of an inputreceived from a user to generate the first window 111 and the secondwindow 112. The device 100 may display different OSes in the firstwindow 111 and the second window 112. For example, OS A 1310 may bedisplayed in the first window 111, and OS C 1330 may be displayed in thesecond window 112.

In FIG. 13B, OS B 1320 may run in the background of the device 100.

The device 100 according to an embodiment may convert the second emailnotification 1322 generated in OS B 1320 running in the background onthe basis of a preset format of an OS selected from between OS A 1310and OS C 1330. For example, the device 100 may select OS C 1330 with lowcomplexity on the basis of a complexity of each of the windows 111 and112 in which OS A 1310 and OS C 1330 are respectively displayed. Here,the complexity may be determined depending on the number of executionwindows that are displayed in a window when an application runs on thedevice 100. In FIG. 13B, two execution windows may be displayed in thefirst window 111 when two notifications 1312 and 1314 are generated inOS A 1310. On the other hand, since there is no execution windowdisplayed in the second window 112, the device 100 may select OS C 1330displayed in the second window 112 with low complexity.

The device 100 according to an embodiment may convert the notification1322 generated in OS B 1320 on the basis of a preset format of theselected OS C 1330. For example, the second email notification 1322 ofOS B 520 may include text indicating a sender of an email and an emailicon image, and the preset format of OS C 1330 may include an email iconimage and text indicating the sender and a reception time. By adding thetext indicating the reception time to the notification 1322 generated inOS B 1320, the device 100 may convert the notification 1322.

The device 100 according to an embodiment may display a convertednotification 1332 at a preset position in the second window 112 of thefirst display 110.

FIG. 14 is a flowchart for describing a method of displaying anotification generated in an OS running in the background of the device100 when a plurality of OSes are displayed by adding the second display115 to the device 100 according to an embodiment.

In step S1410, the device 100 may detect the second display that isadditionally connected to the device 100.

The second display may be connected by wire or wirelessly to the device100 according to an embodiment. Thus, the device 100 may displaydifferent OSes on the first display and the second display.

In step S1420, the device 100 may display a first OS and a fourth OS onthe first display and the second display, respectively.

The device 100 according to an embodiment may select a plurality of OSesto be displayed on the first display and the second display. As anotherexample, the device 100 may receive a selection input from a user anddisplay an OS corresponding to the received selection input on the firstdisplay and the second display.

Meanwhile, step S1420 may correspond to step S610, which has beendescribed above with reference to FIG. 6.

In step S1430, the device 100 may detect a notification generated in asecond OS running in the background of the device 100.

According to an embodiment, when an event occurs in a second applicationrunning on the second OS, a notification may be generated to provideinformation regarding the event to the user.

Meanwhile, step S1430 may correspond to step S220, which has beendescribed above with reference to FIG. 2.

In step S1440, the device 100 may select the first OS from between thefirst OS and the fourth OS when the notification is generated.

The device 100 according to an embodiment may select an OS fordisplaying the generated notification from between the first OS and thefourth OS. As another example, the device 100 may select the first OS onthe basis of a complexity of each of the first display and the seconddisplay in which the first OS and the fourth OS are respectivelydisplayed. As still another example, an OS in which the generatednotification is to be displayed may be preset in the device 100. Asstill another example, the device 100 may select the OS in which thegenerated notification is to be displayed on the basis of the type ofapplication in which the notification is generated.

Meanwhile, step S1440 may correspond to step S630, which has beendescribed above with reference to FIG. 6.

In step S1450, the device 100 may convert the generated notification onthe basis of a format preset for the selected first OS.

Meanwhile, step S1450 may correspond to step S640, which has beendescribed above with reference to FIG. 6.

In step S1460, the device 100 may display the converted notification onthe first display 110 on which the first OS is displayed.

The device 100 according to an embodiment may display the convertednotification at a preset position in a screen area of the first display110. As another example, the device 100 may display the convertednotification on the first display 110 on the basis of a complexity ofthe first display 110. As still another example, the device 100 maydisplay the converted notification on the first display 110 on the basisof the type of converted notification.

Meanwhile, step S1460 may correspond to step S650, which has beendescribed above with reference to FIG. 2.

FIG. 15 is a diagram for describing a method of displaying anotification generated in OSes 1520 and 1530 running in the backgroundof the device 100 when a plurality of OSes 1510 to 1540 are displayed byadding the second display 115 to the device 100 according to anembodiment.

The device 100 according to an embodiment may run the plurality of OSes1510, 1520, 1530, and 1540. Referring to an OS structure 1500 running onthe device 100, among the plurality of OSes 1510, 1520, 1530, and 1540,OS A 1510 is a host OS, and OS B 1520, OS C 1530, and OS D 1540 are eacha guest OS. Here, the method of operating the plurality of OSes 1510,1520, 1530, and 1540 may be the same as described above with referenceto FIG. 3.

Referring to FIG. 15A, when an event occurs in applications running onOS A 1510 of the device 100 according to an embodiment, a notification1512 may be generated. For example, when a message is received in afirst messenger application running on OS A 1510, a first messagenotification 1512 may be generated. Also, when an email is received in afirst email application running on OS B 1520, a second emailnotification 1522 may be generated.

Also, when an email is received in a fourth email application running onOS D 1540, a fourth email notification 1542 may be generated. Also, whena message is received in a fourth messenger application running on OS D1520, a fourth message notification 1544 may be generated.

The device 100 according to an embodiment may display the notification1512 generated in OS A 1510 on the first display 110 on which OS A 1510is displayed. Also, the device 100 may convert the notification 1522generated in OS B 1520 running in the background according to a formatpreset for OS A 1510 and may display the converted notification 1516 onthe first display 110. Also, the device 100 may convert the notification1542 generated in OS D 1540 running in the background according to theformat preset for OS A 1510 and may display the converted notification1518 on the first display 110.

Referring to FIG. 15B, the second display 115 may be additionallyconnected to the device 100 according to an embodiment. The device 100may display different OSes on the first display 110 and the seconddisplay 115 when the second display 115 is additionally connected to thedevice 100. For example, OS A 1510 may be displayed on the first display110, and OS D 1540 may be displayed on the second display 115. Thus, theconverted notifications 1516 and 1518 of a fourth OS may be displayed onthe second display 115 as original notifications 1542 and 1544 beforeconversion.

In FIG. 15B, OS B 1520 and OS C 1530 may run in the background of thedevice 100.

The device 100 according to an embodiment may convert the second emailnotification 1522 generated in OS B 1520 running in the background onthe basis of a preset format of an OS selected from between OS A 1510and OS D 1540. For example, the device 100 may select OS A 1510 on thebasis of a complexity of each of the displays 110 and 115 in which OS A1510 and OS D 1540 are respectively displayed.

In FIG. 15B, one execution window may be displayed on the first display110 when one notification 1512 is generated in OS A 1510. Meanwhile, twoexecution windows may be displayed on the second display 115 when twonotifications 1544 and 1546 are generated in OS D 1540. The device 100may select OS A 1510 displayed on the first display 110 with lowcomplexity.

The device 100 according to an embodiment may convert the notification1522 generated in OS B 1520 on the basis of the preset format of theselected OS A 1510. The device 100 may display the convertednotification 1516 at a preset position in the first display 110.

FIG. 16 is a flowchart for describing a method of displaying anotification generated in an OS running in the background of the device100 when a plurality of OSes displayed on the first display 110 of thedevice 100 are changed according to an embodiment.

In step S1610, the device 100 may display a first OS and a third OS inthe first window 111 and the second window 112 of the first display 110,respectively.

Meanwhile, step S1610 may correspond to step S410, which has beendescribed above with reference to FIG. 4.

In step S1620, the device 100 may display a second OS and the third OSin the first window 111 and the second window 112 of the first display110 on the basis of a change input of a user. Here, the change input ofthe user may include an identification value of an OS that is intendedto be displayed in each window by the user. For example, the changeinput may include identification values of the second OS and the thirdOS.

When the change input of the user is received, the device 100 accordingto an embodiment may stop displaying the first OS. The device 100 maydisplay the third OS in the first window 111 while stopping displayingthe first OS. Thus, the first OS may run in the background of the device100.

In step S1630, the device 100 may detect a notification generated in thefirst OS running in the background of the device 100.

According to an embodiment, when an event occurs in a first applicationrunning on the first OS, a notification may be generated to provideinformation regarding the event to the user.

Meanwhile, step S1630 may correspond to step S420, which has beendescribed above with reference to FIG. 4.

In step S1640, the device 100 may select the second OS from between thesecond OS and the third OS when the notification is generated.

Meanwhile, step S1640 may correspond to step S430, which has beendescribed above with reference to FIG. 4.

In step S1650, the device 100 may convert the generated notification onthe basis of a format preset for the selected second OS.

According to an embodiment, the device 100 may convert the notificationon the basis of the preset format of the second OS displayed in thefirst window to display the generated notification in the first window.

Meanwhile, step S1650 may correspond to step S440, which has beendescribed above with reference to FIG. 4.

In step S1660, the device 100 may display the converted notification inthe first window 111 of the first display 110 on which the second OS isdisplayed.

The device 100 according to an embodiment may display the convertednotification at a preset position in the first window 111. As anotherexample, the device 100 may display the converted notification at adetermined position in the first window 111 on the basis of a complexityof the first window 111. As still another example, the device 100 maydisplay the converted notification at the determined position in thefirst window 111 on the basis of the type of converted notification.

Meanwhile, step S1660 may correspond to step S450, which has beendescribed above with reference to FIG. 4.

FIG. 17 is a diagram for describing a method of displaying anotification generated in an OS running in the background of the device100 when a plurality of OSes displayed on the first display 110 of thedevice 100 are changed according to an embodiment.

The device 100 according to an embodiment may run a plurality of OSes1710, 1720, and 1730. Referring to an OS structure 1700 running on thedevice 100, among the plurality of OSes 1710, 1720, and 1730, OS A 1710is a host OS, and OS B 1720 and OS C 1730 are each a guest OS. Here, themethod of operating the plurality of OSes 1710, 1720, and 1730 may bethe same as described above with reference to FIG. 3.

Referring to FIG. 17A, the device 100 according to an embodiment maydivide a screen area of the first display 110 to generate the firstwindow 111 and the second window 112. The device 100 may displaydifferent OSes in the first window 111 and the second window 112.

For example, OS A 1710 may be displayed in the first window 111, and OSC 1730 may be displayed in the second window 112.

According to an embodiment, OS B 1720 may run in the background of thedevice 100. OS B 1720 which is running in the background may not bedisplayed on the first display 110 of the device 100.

Meanwhile, when an event occurs in applications of the plurality of OSes1710, 1720, and 1730 installed in the device 100, notifications 1712,1732, and 1734 may be generated.

For example, when a message is received in a first messenger applicationrunning on OS A 1710, a first message notification 1712 may begenerated. Also, when an email is received in a third email applicationrunning on OS C 1730, a third email notification 1732 may be generated.

The device 100 according to an embodiment may display the notification1712 generated in OS A 1710 in the first window 111 in which OS A 1710is displayed. Also, the device 100 may display the notification 1732generated in OS C 1730 in the second window 112 in which OS C 1730 isdisplayed.

Referring to FIG. 17B, when a change input of a user is received, thedevice 100 may stop displaying OS A 1710. The device 100 according to anembodiment may display OS B 1720 selected according to the change inputof the user in the first window 111 which stops displaying OS A 1710.Thus, OS A 1710 may run in the background of the device 100.

The device 100 according to an embodiment may detect the first messagenotification 1712 generated in OS A 1710 running in the background. Thedevice 100 according to an embodiment may convert the generated firstmessage notification 1712 on the basis of a preset format of an OSselected from between OS A 1710 and OS C 1730. For example, the device100 may select OS B 1720 with low complexity on the basis of complexityof each of the windows 111 and 112 in which OS B 1720 and OS C 1730 arerespectively displayed.

Here, the complexity may be determined depending on the number ofexecution windows that are displayed in the windows when an applicationruns on the device 100.

The device 100 according to an embodiment may convert the notification1712 generated in OS A 1710 on the basis of a preset format of theselected OS B 1730. For example, for the first message notification 1712of OS A 1710, a message icon image may be arranged on the left side. Forthe preset format of OS B 1720, a message icon image may be arranged onthe right side. By changing the position of the message icon image ofthe notification 1712 generated in OS A 1710 to the right side, thedevice may convert a notification 1712.

The device 100 according to an embodiment may display a convertednotification 1722 at a preset position in the first window 112 in whichOS B 1720 is displayed.

FIGS. 18 and 19 are block diagrams showing a device 1800 with aplurality of OSes installed therein according to an embodiment.

As shown in FIG. 18, a device 1800 according to an embodiment of thepresent invention may include a first display 1810 and a controller1820. However, not all of the elements shown in this figure areessential. The device 1800 may be implemented by more or less elementsthan those shown in the figure.

For example, as shown in FIG. 19, the device 1800 according to anembodiment of the present invention may further include a communicator1830, a user input unit 1840, a sensing unit 1850, an output unit 1860,an audio/video (A/V) input unit 1870, and a memory 1880 in addition tothe first display 1810 and the controller 1820.

Meanwhile, the device 1800 of FIGS. 18 and 19 may correspond to thedevice 100 that has been described above with reference to FIGS. 1 to17.

The above elements will be described below in sequence.

The first display 1810 according to an embodiment displays at least oneof a plurality of OSes.

For example, the first display 1810 may display a first OS among theplurality of OSes. Also, the first display 1810 may display an OS ineach window which is obtained by dividing a screen area of the firstdisplay 1810. For example, the first OS may be displayed in a firstwindow (not shown) of the first display 1810, and a third OS may bedisplayed in a second window (not shown).

However, the first OS, a second OS, and the third OS are merely examplesfor describing the plurality of OSes displayed on the first display1810. Accordingly, the present invention is not limited thereto.

A notification generated in the first OS may be displayed on the firstdisplay 1810 according to an embodiment. Also, when a notification ofthe second OS running in the background of the device is converted bythe controller 1820, the first display 1810 may display the convertednotification.

The first display 1810 according to an embodiment outputs informationthat has been processed by the device 1800. For example, the firstdisplay 1810 may receive at least some of received images. The firstdisplay 1810 may display an image of a received screen at one sidethereof.

When the first display 1810 and a touchpad form a layered structure toconfigure a touch screen, the first display 1810 may also be used as aninput device as well as an output unit.

The first display 1810 may include at least one of a liquid crystaldisplay (LCD), a thin film transistor-LCD (TFT-LCD), an organiclight-emitting diode (OLED), a flexible display, a three-dimensional(3D) display, and an electrophoretic display. The device 1800 mayfurther include one or more displays in addition to the first display1810 according to an implementation of the device 1800.

Typically, the controller 1820 controls an overall operation of thedevice 1800. For example, the controller 1820 may generally control thefirst display 1810, the communicator 1830, the user input unit 1840, thesensing unit 1850, the output unit 1860, the A/V input unit 1870, andthe memory 1880 by executing programs stored in the memory 1880.

The controller 1820 according to an embodiment identifies the first OSthat is displayed on the first display 1810. Also, the controller 1820detects a notification that is generated in the second OS running in thebackground of a device among a plurality of OSes. The controller 1820according to an embodiment may convert the detected notification on thebasis of a preset format of the first OS that is displayed on the firstdisplay 1810. The controller 1820 may control the first display 1810such that the converted notification is displayed on the first display1810.

The controller 1820 according to an embodiment may control communicationbetween the plurality of OSes stored in the memory 1880. Here, it isassumed that, among the plurality of OSes, the first OS is a host OS,and the other OSes are each a guest OS.

For example, when a notification is generated in the second OS runningin the background of the device 1800, the controller 1820 may deliverinformation regarding the notification to the first OS. The controller1820 may control the first OS to convert the notification generated inthe second OS on the basis of the preset format of the first OS.According to this embodiment, the notification generated in the secondOS may be converted in the first OS.

As another example, when a notification is generated in the second OSrunning in the background of the device 1800, the controller 1820 maycontrol the second OS to convert the generated notification on the basisof the format of the first OS that is being displayed on the display1810. According to this embodiment, the notification generated in thesecond OS may be converted in the second OS and then delivered to thefirst OS.

As still another example, when a notification is generated in the secondOS running in the background of the device 1800, the controller 1820 maycontrol the first OS, which is the host OS, to convert the generatednotification on the basis of a format of the third OS that is beingdisplayed on the display 1810. According to this embodiment, thenotification generated in the second OS may be converted in the firstOS, which serves as an intermediary, and then delivered to the third OS.

When a plurality of OSes, that is, the first OS and the third OS, aredisplayed on the first display 1810, the controller 1820 according to anembodiment may select an OS that is a criterion for converting thenotification of the second OS running in the background of the device1800. For example, the controller 1820 may select one of the first OSand the third OS on the basis of priority information preset for theplurality of OSes. As another example, the controller 1820 may selectone OS on the basis of a complexity of windows in which the first OS andthe third OS are respectively displayed. As still another example, thecontroller 1820 may select one of the first OS and the third OS on thebasis of OS information preset for the second OS in which thenotification is generated.

The controller 1820 according to an embodiment may detect a seconddisplay of an external device connected to the device 1800. Thecontroller 1820 may select a fourth OS from among the plurality of OSesand display the selected fourth OS on the second display.

When a plurality of OSes, that is, the first OS and the fourth OS, aredisplayed on the first display 1810 and the second display,respectively, the controller 1820 may select an OS that is a criterionfor converting the notification of the second OS running in thebackground of the device 1800. For example, the controller 1820 mayselect one of the first OS and the fourth OS on the basis of priorityinformation preset for the plurality of OSes.

As another example, the controller 1820 may select one OS on the basisof a complexity of each of displays on which the first OS and the fourthOS are respectively displayed. As still another example, the controller1820 may select one OS on the basis of the type of each of the displayson which the first OS and the fourth OS are displayed. As still anotherexample, the controller 1820 may select one of the first OS and thethird OS on the basis of OS information preset for the second OS inwhich the notification is generated.

The controller 1820 according to an embodiment may determine an OS to bedisplayed, on the basis of a selection input received from a user. Also,the controller 1820 according to an embodiment may change an OS to bedisplayed, on the basis of a change input received from a user.

The communicator 1830 may include one or more elements for communicatingbetween the device 1800 and the second display of the external device.For example, the communicator 1830 may include a short-range wirelesscommunicator 1831, a mobile communicator 1832, and a broadcast receiver1833.

The short-range wireless communicator 1831 may include, but is notlimited to, a Bluetooth communicator, a Bluetooth Low Energy (BLE)communicator, a near field communication (NFC) unit, a wireless localarea network (WLAN) communicator, a Zigbee communicator, an InfraredData Association (IrDA) communicator, a Wi-Fi Direct (WFD) communicator,an ultra wideband (UWB) communicator, an Ant+ communicator, etc.

The mobile communicator 1832 transmits and receives a radio signal toand from at least one of a base station, an external terminal, and aserver over a mobile communication network.

Here, the radio signal may include a voice call signal, a video callsignal, or various types of data according to a transmission and/orreception of text and/or multimedia messages.

The broadcast receiver 1833 receives a broadcast signal and/orbroadcast-related information from the outside over a broadcast channel.The broadcast channel may include a satellite channel and a terrestrialchannel. Depending on implementation, the device 1800 may not includethe broadcast receiver 1833.

The user input unit 1840 refers to a means used by the user to enterdata for controlling the device 1800. For example, the user input unit1840 may include, but is not limited to, a key pad, a dome switch, atouchpad (a contact capacitance type, a pressure resistance type, aninfrared sensing type, a surface ultrasonic wave conduction type, anintegral tension measurement type, a piezoelectric effect type, etc.), ajog wheel, a jog switch, etc.

The user input unit 1840 according to an embodiment may receive aselection input for selecting an OS to be displayed on at least one ofthe first display and the second display, among the plurality of OSesinstalled in the device 1800. Also, the user input unit 1840 may receivea change input for changing an OS to be displayed on at least one of thefirst display and the second display. Meanwhile, this is merely anembodiment of the present invention.

The user input unit 1840 may receive a user input needed to perform anoperation of the device 1800, which has been described above withreference to FIGS. 1 to 17.

The sensing unit 1850 may include, but is not limited to, at least oneof a magnetic sensor 1851, an acceleration sensor 1852, atemperature/humidity sensor 1853, an infrared sensor 1854, a gyroscopesensor 1855, a positioning sensor (e.g., a Global Positioning System(GPS) sensor) 1856, an air pressure sensor 1857, a proximity sensor1858, and an RGB sensor (that is, an illumination sensor) 1859. Afunction of each of the sensors may be directly inferred from its nameby those skilled in the art, and thus a detailed description thereofwill be omitted.

The output unit 1860 is used to perform an operation determined by thecontroller 1820 and may include a sound output unit 1861, a vibrationmotor 1862, etc. However, this is merely one embodiment. As anotherexample, the output unit 1860 may include the display 1810.

The sound output unit 1861 outputs audio data that is received from thecommunicator 1830 or stored in the memory 1880. Also, the sound outputunit 1861 outputs a sound signal associated with a function (e.g., acall signal received sound, a message received sound, or a notificationsound) performed by the device 1800. The sound output unit 1861 mayinclude a speaker, a buzzer, etc.

The vibration motor 1862 may output a vibration signal. For example, thevibration motor 753 may output a vibration signal corresponding to anoutput of audio data or video data (e.g., the call signal receivedsound, the message received sound, etc.). Also, the vibration motor 753may output the vibration signal when a touch is input to the touchscreen.

The A/V input unit 1870 is used to enter an audio signal or video signaland may include a camera 1871, a microphone 1872, etc. The camera 1871may obtain an image frame of a still image or a moving image through animage sensor in a video call mode or in a photographing mode. The imagecaptured through the image sensor may be processed through thecontroller 1820 or a separate image processing unit (not shown).

The image frame processed by the camera 1871 may be stored in the memory1880 or transmitted to the outside through the communicator 1830. Thecamera 1871 may be provided as two or more cameras according to anaspect of the configuration of the device.

The microphone 1872 receives an external sound signal and processes thereceived external sound signal into electrical voice data. For example,the microphone 1872 may receive a sound signal from an external deviceor a talker. The microphone 1872 may use various noise removalalgorithms for removing noise generated while receiving the externalsound signal.

The memory 1880 may store processing and controlling programs of thecontroller 1820 or may store input/output data.

The memory 1880 according to an embodiment may store a plurality ofOSes. Also, the memory 1880 may store applications running on each ofthe plurality of OSes. Also, the memory 1880 may store a virtual machinefor running each of the plurality of OSes.

The memory 1880 according to an embodiment may store priorityinformation preset for the plurality of OSes.

The memory 1880 may include at least one storage medium among a flashmemory type memory, a hard disk type memory, a multimedia card microtype memory, a card type memory (e.g., a secure digital (SD) or extremedigital (XD) memory), a random access memory (RAM), a static randomaccess memory (SRAM), a read-only memory (ROM), an electrically erasableprogrammable read-only memory (EEPROM), a programmable read-only memory(PROM), a magnetic memory, a magnetic disk, and an optical disc. Also,the device 1800 may operate a web storage device or a cloud server thatperforms a storage function of the memory 1880 over the Internet.

Programs stored in the memory 1880 may be classified into a plurality ofmodules according to their functions and, for example, may be classifiedinto a user interface (UI) module 1881, a touch screen module 1882, anotification module 1883, etc.

The UI module 1881 may provide an application-specific UI, graphic userinterface (GUI), or the like that is linked with the device 1800. Thetouch screen module 1882 may detect a touch gesture of a user on thetouch screen and deliver information regarding the touch gesture to thecontroller 1820. The touch screen module 1882 according to an embodimentof the present invention may recognize and analyze a touch code. Thetouch screen module 1882 may also be configured as separate hardwareincluding a controller.

Various sensors may be provided inside or near the touch screen todetect a touch or a proximity touch on the touch screen. An example of asensor for detecting a touch on the touch screen is a tactile sensor.The tactile sensor refers to a sensor for detecting a contact of aspecific object to such a degree that a human may feel the contact withthe specific object or to a higher degree. The tactile sensor may detectvarious types of information such as a roughness of a contact surface, ahardness of a contact object, a temperature at a contact point, etc.

Also, an example of a sensor for detecting a touch on the touch screenis a proximity sensor.

The proximity sensor refers to a sensor for detecting an object that isapproaching a predetermined detection surface or a neighboring objectwithout mechanical contact by using electromagnetic force or infraredlight. Examples of the proximity sensor include a transmissivephotoelectric sensor, a direct reflective photoelectric sensor, a mirrorreflective photoelectric sensor, a high-frequency oscillation proximitysensor, a capacitive proximity sensor, a magnetic proximity sensor, andan infrared proximity sensor. Examples of the touch gesture of the usermay include a tap, a touch and hold, a double tap, a drag, a pan, aflick, a drag and drop, a swipe, etc.

The notification module 1883 may generate a signal which notifies of anoccurrence of an event in the device 1800. Examples of the eventoccurring in the device 1800 may include an acquisition or reception ofnew information by an application, a reception of a call signal, areception of a message, an input of a key signal, a notification of aschedule, an acquisition of a user input, etc. The notification module1883 may also output a notification signal in the form of a video signalthrough the first display 1810, output a notification signal in the formof an audio signal through the sound output unit 1861, and output anotification signal in the form of a vibration signal through thevibration motor 1863.

The device according to the disclosed embodiment may include aprocessor, a memory for storing and executing program data, a permanentstorage such as a disk drive, a communication port for communicatingwith external devices, UI devices such as a touch panel, keys, andbuttons, etc. When software modules or algorithms are involved, thesesoftware modules or algorithms may be stored as program instructions orcomputer-readable codes executable in the processor in acomputer-readable recording medium. Examples of the computer-readablerecording medium include magnetic storage media (e.g., a ROM, a RAM, afloppy disk, a hard disk, etc.), optical recording media (e.g., acompact disc read-only memory (CD-ROM), a digital versatile disc (DVD),etc.), and so on. The computer-readable recording medium may bedistributed over network-coupled computer systems so that thecomputer-readable code is stored and executed in a distributed fashion.The media can be read by the computer, stored in the memory, andexecuted by the processor.

In the disclosed embodiment, all references, including publications,patent applications, and patents cited herein are hereby incorporated byreference to an extent as if each reference were individually andspecifically indicated to be incorporated by reference and were setforth in its entirety herein.

For the purposes of promoting an understanding of the embodiments,reference has been made to embodiments illustrated in the drawings, andspecific language has been used to describe the embodiments. However, nolimitation of the scope of the embodiments is intended by this specificlanguage, and the embodiments should be construed as encompassing allembodiments that would normally occur to one of ordinary skill in theart.

The embodiments may be described in terms of functional block componentsand various processing steps. Such functional blocks may be realized byany number of hardware and/or software components configured to performthe specified functions. For example, the embodiments may employ variousintegrated circuit (IC) components, e.g., memory elements, processingelements, logic elements, look-up tables, and the like, which may carryout a variety of functions under the control of one or moremicroprocessors or other control devices.

Similarly, where the elements of the embodiments are implemented usingsoftware programming or software elements, the embodiments may beimplemented with any programming or scripting language such as C, C++,Java, assembler, or the like with the various algorithms beingimplemented with any combination of data structures, objects, processes,routines or other programming elements. Functional aspects may beimplemented in algorithms that execute on one or more processors. Also,embodiments may employ any number of conventional techniques forelectronic configuration, signal processing and/or control, dataprocessing and the like. The terms “mechanism,” “element,” “means,” and“configuration” are used broadly and are not limited to mechanical orphysical components, but may include software routines in conjunctionwith processors or the like.

The particular implementations shown and described herein areillustrative examples and are not intended to otherwise limit the scopeof the embodiments in any way. Indeed, for the sake of brevity,conventional electronic components, control systems, software, and otherfunctional aspects of the systems may not be described in detail.Furthermore, the connecting lines or connectors shown in the variouspresented figures are intended to represent exemplary functionalrelationships, physical connections, or logical couplings between thevarious elements. It should be noted that many alternative or additionalfunctional relationships, physical connections or logical connectionsmay be present in a practical apparatus. Moreover, no item or componentis essential to the practice of the embodiments unless the element isspecifically described as “essential” or “critical.”

What is claimed is:
 1. A method of displaying a notification on adevice, the method comprising: displaying a first OS on a display of thedevice; acquiring an event notification generated in a second OS runningin an external device in response to an event occurring in the secondOS; generating a user interface of the event notification based on aformat preset for the first OS; and displaying the generated userinterface of the event notification on the display on which the first OSis displayed to provide information regarding the event.
 2. The methodof claim 1, further comprising: displaying the first OS and a third OSon the display; and selecting an OS from between the first OS and thethird OS when the event notification is acquired, wherein the generatingof the user interface of the event notification comprises generating theuser interface of the event notification based on a format preset forthe selected OS.
 3. The method of claim 2, further comprising dividing ascreen area of the display into a first window for displaying the firstOS and a second window for displaying the third OS.
 4. The method ofclaim 3, wherein the selecting of the OS comprises selecting the OSbased on a complexity of each of the first window and the second window.5. The method of claim 3, further comprising: stopping displaying thethird OS in the second window; running the third OS in a background ofthe device; and generating a user interface of another eventnotification based on the format preset for the first OS when the otherevent notification is generated in at least one of the second OS and thethird OS.
 6. The method of claim 1, further comprising: stoppingdisplaying the first OS on the display; displaying the second OS on thedisplay; detecting an event notification generated in the first OS;generating a user interface of the detected event notification based ona format preset for the second OS; and displaying the generated userinterface of the event notification generated in the first OS.
 7. Themethod of claim 1, wherein the acquiring of the event notificationcomprises receiving the event notification generated in the second OSrunning in the external device communicating with the device.
 8. Anon-transitory computer-readable storage medium storing instructionsthat are executable by a processor, the instructions comprising:instructions to display a first OS on a display of a device;instructions to acquire an event notification generated in a second OSrunning in an external device in response to an event occurring in thesecond OS; instructions to generate a user interface of the eventnotification based on a format preset for the first OS; and instructionsto display the generated user interface of the event notification on thedisplay on which the first OS is displayed to provide informationregarding the event.
 9. A device comprising: a display; and at least oneprocessor configured to: control the display to display a first OS,acquire an event notification generated in a second OS running in anexternal device in response to an event occurring in the second OS,generate a user interface of the event notification based on a formatpreset for the first OS, and control the display to display thegenerated user interface of the event notification on the display onwhich the first OS is displayed to provide information regarding theevent.
 10. The device of claim 9, wherein the at least one processor isconfigured to: control the display to display the first OS and a thirdOS, select an OS from between the first OS and the third OS when thenotification is acquired, and generate the user interface of the eventnotification based on a format preset for the selected OS.
 11. Thedevice of claim 10, wherein the at least one processor is configured to:divide a screen area of the display into a first window and a secondwindow, and control the display to display the first OS in the firstwindow and a third OS in the second window.
 12. The device of claim 11,wherein the at least one processor is configured to select the OS basedon a complexity of each of the first window and the second window. 13.The device of claim 11, wherein the at least one processor is configuredto: stop displaying the third OS in the second window, run the third OSin a background of the device, and generate a user interface of anotherevent notification based on the format preset for the first OS when theother event notification is generated in at least one of the second OSand the third OS.
 14. The device of claim 9, wherein the at least oneprocessor is configured to: control the display to stop displaying thefirst OS, control the display to display the second OS, detect an eventnotification generated in the first OS, generate a user interface of thedetected event notification based on a format preset for the second OS,and control the display to display the generated user interface of theevent notification generated in the first OS.
 15. The device of claim 9,further comprises a communicator, wherein the at least one processor isconfigured to receive the event notification generated in the second OSrunning in the external device communicating with the device through thecommunicator.